Skip to content

Comments

OCPBUGS-77093: Fixup e830 DPLL detection and ignore flags#551

Open
lack wants to merge 1 commit intoopenshift:release-4.21from
lack:ignore_e830_dpll-4.21
Open

OCPBUGS-77093: Fixup e830 DPLL detection and ignore flags#551
lack wants to merge 1 commit intoopenshift:release-4.21from
lack:ignore_e830_dpll-4.21

Conversation

@lack
Copy link
Member

@lack lack commented Feb 19, 2026

This ensures that e830 DPLL is properly detected and properly ignored in
all scenarios.

Signed-off-by: Jim Ramsay jramsay@redhat.com
(cherry picked from commit e1da42d)

@lack
Fixup e830 DPLL detection and ignore flags
c2f4435 
This ensures that e830 DPLL is properly detected and properly ignored in
all scenarios.

Signed-off-by: Jim Ramsay <jramsay@redhat.com>
(cherry picked from commit e1da42d)
@openshift-ci openshift-ci bot requested review from SchSeba and aneeshkp February 19, 2026 21:35
@lack
Copy link
Member Author

lack commented Feb 19, 2026

/jira cherry-pick OCPBUGS-77038

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 19, 2026

@lack: Jira Issue OCPBUGS-77038 has been cloned as Jira Issue OCPBUGS-77093. Will retitle bug to link to clone.
/retitle OCPBUGS-77093: Fixup e830 DPLL detection and ignore flags

Details

In response to this:

/jira cherry-pick OCPBUGS-77038

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title Fixup e830 DPLL detection and ignore flags OCPBUGS-77093: Fixup e830 DPLL detection and ignore flags Feb 19, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 19, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 19, 2026

@lack: This pull request references Jira Issue OCPBUGS-77093, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-77038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
  • expected dependent Jira Issue OCPBUGS-77038 to target a version in 4.22.0, but it targets "4.22" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This ensures that e830 DPLL is properly detected and properly ignored in
all scenarios.

Signed-off-by: Jim Ramsay jramsay@redhat.com
(cherry picked from commit e1da42d)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@lack
Copy link
Member Author

lack commented Feb 19, 2026

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 19, 2026

@lack: This pull request references Jira Issue OCPBUGS-77093, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-77038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@lack
Copy link
Member Author

lack commented Feb 19, 2026

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 19, 2026

@lack: This pull request references Jira Issue OCPBUGS-77093, which is invalid:

  • expected dependent Jira Issue OCPBUGS-77038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@lack
Copy link
Member Author

lack commented Feb 19, 2026

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 19, 2026
@lack
Copy link
Member Author

lack commented Feb 19, 2026

/verified later @Bonnie-Block

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Feb 19, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 19, 2026

@lack: This PR has been marked to be verified later by @bonnie-block.

Details

In response to this:

/verified later @Bonnie-Block

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@josephdrichard
Copy link
Contributor

josephdrichard commented Feb 19, 2026

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 19, 2026
@josephdrichard
Copy link
Contributor

josephdrichard commented Feb 20, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2026

@lack: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

nocturnalastro
nocturnalastro approved these changes Feb 23, 2026
View reviewed changes
Copy link
Contributor

@nocturnalastro nocturnalastro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josephdrichard, lack, nocturnalastro

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [josephdrichard,nocturnalastro]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lack
Copy link
Member Author

lack commented Feb 25, 2026

/cherry-pick release-4.20

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Feb 25, 2026

@lack: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@lack
Copy link
Member Author

lack commented Feb 25, 2026

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 25, 2026

@lack: This pull request references Jira Issue OCPBUGS-77093, which is invalid:

  • expected dependent Jira Issue OCPBUGS-77038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aneeshkp aneeshkp Awaiting requested review from aneeshkp

@SchSeba SchSeba Awaiting requested review from SchSeba

1 more reviewer

@nocturnalastro nocturnalastro nocturnalastro approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@mffiedler mffiedler

@rbbratta rbbratta

@gsr-shanks gsr-shanks

@weliang1 weliang1

@anuragthehatter anuragthehatter

@huiran0826 huiran0826

@asood-rh asood-rh

@jechen0648 jechen0648

@obochan-rh obochan-rh

@qiowang721 qiowang721

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.